@pmuens you can see this PR plz ? Thank a lot

I was about to open the same PR, thanks @CaptainJojo!

Question: Is it possible to add the entryPoint to the function object?

functions:
  images:
    handler: images
    entryPoint: myExportedFunction #defaults to handler
    events:
      - http: path

Based on your PR, I've ended up writing my own one (PR #98) , because I found that yours was changing the logic a lot, which is breaking changes to anybody already using that plugin. Cheers!

Yes thank, I prefer your PR they are no breaking change :)

@CaptainJojo fun fact, i think your PR was a must as well hehe, but should be optional by passing an option in the serverless.yml, e.g. prependStage: true and prependService: true. (and make sure the serverless remove [function] command is still able to remove it back

@markmssd ok I check that :)

Thanks :D

You think is mandatory use service ? Just stage is enought ?

In my opinion I think it is, so there is no conflicts in naming when 2 functions have the same name.

We can compare with the AWS plugin to see if it also adds the service name etc.

ok It's finish with prependStage, I continue to use preprendService

Awesome thanks!! @pmuens any thoughts on that?

@markmssd @pmuens it's ok :)

@pmuens ?

FYI, I proceeded to fork this project (https://github.com/digital-dynamite/serverless-google-cloudfunctions-awesome) (npm link) and have it include all our changes.

So what I have more:

• the provider.credentials can take the Service Key file as variable, not only as a file path.
  e.g. provider.credentials: ${self:custom.GCLOUD_SERVICE_KEY} (custom is actually a js file which converts the base64 Service Key to JSON. This is to allow easy CICD from CircleCI, or any CI platform.

• serverless deploy --prependStage --stage red will deploy all functions with the red stage prepended

• Same thing with the service, with --prependService

Thanks again @CaptainJojo !